-- Network Working Group J. Flick
-- Request for Comments: 3636 Hewlett-Packard Company
-- Obsoletes: 2668, 1515 September 2003
-- Category: Standards Track-- Definitions of Managed Objects for
-- IEEE 802.3 Medium Attachment Units (MAUs)MAU-MIB DEFINITIONS::=BEGINIMPORTSCounter32,Integer32,Counter64,OBJECT-TYPE,MODULE-IDENTITY,NOTIFICATION-TYPE,OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI
TruthValue,AutonomousType,TEXTUAL-CONVENTIONFROM SNMPv2-TC
OBJECT-GROUP,MODULE-COMPLIANCE,NOTIFICATION-GROUPFROM SNMPv2-CONF
InterfaceIndexFROM IF-MIB;mauMod MODULE-IDENTITYLAST-UPDATED"200309190000Z"-- September 19, 2003ORGANIZATION"IETF Ethernet Interfaces and Hub MIB
Working Group"CONTACT-INFO
"WG E-mail: hubmib@ietf.org
To subscribe: hubmib-request@ietf.org
Chair: Dan Romascanu
Postal: Avaya Inc.
Atidim Technology Park, Bldg. 3
Tel Aviv 61131
Israel
Tel: +972 3 645 8414
E-mail: dromasca@avaya.com
Editor: John Flick
Postal: Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557
USA
Tel: +1 916 785 4018
Fax: +1 916 785 1199
E-mail: johnf@rose.hp.com"DESCRIPTION"Management information for 802.3 MAUs.
The following reference is used throughout
this MIB module:
[IEEE 802.3 Std] refers to:
IEEE Std 802.3, 2002 Edition: 'IEEE Standard
for Information technology -
Telecommunications and information exchange
between systems - Local and metropolitan
area networks - Specific requirements -
Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method
and physical layer specifications', as
amended by IEEE Std 802.3ae-2002:
'Amendment: Media Access Control (MAC)
Parameters, Physical Layer, and Management
Parameters for 10 Gb/s Operation', August,
2002.
Of particular interest is Clause 30, '10Mb/s,
100Mb/s, 1000Mb/s and 10 Gb/s Management'.
Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC 3636;
see the RFC itself for full legal notices."REVISION"200309190000Z"-- September 19, 2003
DESCRIPTION"Updated to include support for 10 Gb/s MAUs.
This resulted in the following revisions:
- Added OBJECT-IDENTITY definitions for
10 gigabit MAU types
- Added fiberLC jack type to JackType TC
- Extended ifMauTypeListBits with bits for
the 10 gigabit MAU types
- Added enumerations to ifMauMediaAvailable,
and updated its DESCRIPTION to reflect
behaviour at 10 Gb/s
- Added 64-bit version of ifMauFalseCarriers
and added mauIfGrpHCStats object group to
contain the new object
- Deprecated mauModIfCompl2 and replaced it
with mauModIfCompl3, which includes the new
object group
This version published as RFC 3636."REVISION"199908240400Z"-- August 24, 1999DESCRIPTION"This version published as RFC 2668. Updated
to include support for 1000 Mb/sec
MAUs and flow control negotiation."REVISION"199710310000Z"-- October 31, 1997DESCRIPTION"Version published as RFC 2239."REVISION"199309300000Z"-- September30, 1993DESCRIPTION"Initial version, published as RFC 1515."::={ snmpDot3MauMgt 6}snmpDot3MauMgt OBJECTIDENTIFIER::={ mib-2 26}
-- textual conventionsJackType::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"Common enumeration values for repeater
and interface MAU jack types."SYNTAXINTEGER{other(1),rj45(2),rj45S(3),-- rj45 shieldeddb9(4),bnc(5),fAUI(6),-- female auimAUI(7),-- male auifiberSC(8),fiberMIC(9),fiberST(10),telco(11),mtrj(12),-- fiber MT-RJ
hssdc(13),-- fiber channel style-2fiberLC(14)}dot3RpMauBasicGroup
OBJECTIDENTIFIER::={ snmpDot3MauMgt 1}dot3IfMauBasicGroup
OBJECTIDENTIFIER::={ snmpDot3MauMgt 2}dot3BroadMauBasicGroup
OBJECTIDENTIFIER::={ snmpDot3MauMgt 3}dot3IfMauAutoNegGroup
OBJECTIDENTIFIER::={ snmpDot3MauMgt 5}-- object identities for MAU types-- (see rpMauType and ifMauType for usage)dot3MauType
OBJECTIDENTIFIER::={ snmpDot3MauMgt 4}dot3MauTypeAUI OBJECT-IDENTITYSTATUScurrentDESCRIPTION"no internal MAU, view from AUI"REFERENCE"[IEEE 802.3 Std.], Section 7"::={ dot3MauType 1}dot3MauType10Base5 OBJECT-IDENTITY
STATUScurrentDESCRIPTION"thick coax MAU"REFERENCE"[IEEE 802.3 Std.], Section 7"::={ dot3MauType 2}dot3MauTypeFoirl OBJECT-IDENTITYSTATUScurrentDESCRIPTION"FOIRL MAU"REFERENCE"[IEEE 802.3 Std.], Section 9.9"::={ dot3MauType 3}dot3MauType10Base2 OBJECT-IDENTITYSTATUScurrentDESCRIPTION"thin coax MAU"REFERENCE"[IEEE 802.3 Std.], Section 10"::={ dot3MauType 4}dot3MauType10BaseT OBJECT-IDENTITYSTATUScurrentDESCRIPTION"UTP MAU.
Note that it is strongly recommended that
agents return either dot3MauType10BaseTHD or
dot3MauType10BaseTFD if the duplex mode is
known. However, management applications should
be prepared to receive this MAU type value from
older agent implementations."REFERENCE"[IEEE 802.3 Std.], Section 14"::={ dot3MauType 5}
dot3MauType10BaseFP OBJECT-IDENTITYSTATUScurrentDESCRIPTION"passive fiber MAU"REFERENCE"[IEEE 802.3 Std.], Section 16"::={ dot3MauType 6}dot3MauType10BaseFB OBJECT-IDENTITYSTATUScurrentDESCRIPTION"sync fiber MAU"REFERENCE"[IEEE 802.3 Std.], Section 17"::={ dot3MauType 7}dot3MauType10BaseFL OBJECT-IDENTITYSTATUScurrentDESCRIPTION"async fiber MAU.
Note that it is strongly recommended that
agents return either dot3MauType10BaseFLHD or
dot3MauType10BaseFLFD if the duplex mode is
known. However, management applications should
be prepared to receive this MAU type value from
older agent implementations."REFERENCE"[IEEE 802.3 Std.], Section 18"::={ dot3MauType 8}dot3MauType10Broad36 OBJECT-IDENTITYSTATUScurrentDESCRIPTION"broadband DTE MAU.
Note that 10BROAD36 MAUs can be attached to
interfaces but not to repeaters."REFERENCE"[IEEE 802.3 Std.], Section 11"
::={ dot3MauType 9}------ new since RFC 1515:dot3MauType10BaseTHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"UTP MAU, half duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 14"::={ dot3MauType 10}dot3MauType10BaseTFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"UTP MAU, full duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 14"::={ dot3MauType 11}dot3MauType10BaseFLHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"async fiber MAU, half duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 18"::={ dot3MauType 12}dot3MauType10BaseFLFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"async fiber MAU, full duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 18"::={ dot3MauType 13}
dot3MauType100BaseT4 OBJECT-IDENTITYSTATUScurrentDESCRIPTION"4 pair category 3 UTP"REFERENCE"[IEEE 802.3 Std.], Section 23"::={ dot3MauType 14}dot3MauType100BaseTXHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"2 pair category 5 UTP, half duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 25"::={ dot3MauType 15}dot3MauType100BaseTXFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"2 pair category 5 UTP, full duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 25"::={ dot3MauType 16}dot3MauType100BaseFXHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"X fiber over PMT, half duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 26"::={ dot3MauType 17}dot3MauType100BaseFXFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"X fiber over PMT, full duplex mode"
REFERENCE"[IEEE 802.3 Std.], Section 26"::={ dot3MauType 18}dot3MauType100BaseT2HD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"2 pair category 3 UTP, half duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 32"::={ dot3MauType 19}dot3MauType100BaseT2FD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"2 pair category 3 UTP, full duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 32"::={ dot3MauType 20}------ new since RFC 2239:dot3MauType1000BaseXHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"PCS/PMA, unknown PMD, half duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 36"::={ dot3MauType 21}dot3MauType1000BaseXFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"PCS/PMA, unknown PMD, full duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 36"::={ dot3MauType 22}
dot3MauType1000BaseLXHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Fiber over long-wavelength laser, half duplex
mode"REFERENCE"[IEEE 802.3 Std.], Section 38"::={ dot3MauType 23}dot3MauType1000BaseLXFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Fiber over long-wavelength laser, full duplex
mode"REFERENCE"[IEEE 802.3 Std.], Section 38"::={ dot3MauType 24}dot3MauType1000BaseSXHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Fiber over short-wavelength laser, half
duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 38"::={ dot3MauType 25}dot3MauType1000BaseSXFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Fiber over short-wavelength laser, full
duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 38"::={ dot3MauType 26}
dot3MauType1000BaseCXHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Copper over 150-Ohm balanced cable, half
duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 39"::={ dot3MauType 27}dot3MauType1000BaseCXFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Copper over 150-Ohm balanced cable, full
duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 39"::={ dot3MauType 28}dot3MauType1000BaseTHD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Four-pair Category 5 UTP, half duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 40"::={ dot3MauType 29}dot3MauType1000BaseTFD OBJECT-IDENTITYSTATUScurrentDESCRIPTION"Four-pair Category 5 UTP, full duplex mode"REFERENCE"[IEEE 802.3 Std.], Section 40"::={ dot3MauType 30}------ new since RFC 2668:dot3MauType10GigBaseX OBJECT-IDENTITY
STATUScurrentDESCRIPTION"X PCS/PMA, unknown PMD."REFERENCE"[IEEE 802.3 Std.], Section 48"::={ dot3MauType 31}dot3MauType10GigBaseLX4 OBJECT-IDENTITYSTATUScurrentDESCRIPTION"X fiber over WWDM optics"REFERENCE"[IEEE 802.3 Std.], Section 53"::={ dot3MauType 32}dot3MauType10GigBaseR OBJECT-IDENTITYSTATUScurrentDESCRIPTION"R PCS/PMA, unknown PMD."REFERENCE"[IEEE 802.3 Std.], Section 49"::={ dot3MauType 33}dot3MauType10GigBaseER OBJECT-IDENTITYSTATUScurrentDESCRIPTION"R fiber over 1550 nm optics"REFERENCE"[IEEE 802.3 Std.], Section 52"::={ dot3MauType 34}dot3MauType10GigBaseLR OBJECT-IDENTITYSTATUScurrentDESCRIPTION"R fiber over 1310 nm optics"REFERENCE"[IEEE 802.3 Std.], Section 52"
::={ dot3MauType 35}dot3MauType10GigBaseSR OBJECT-IDENTITYSTATUScurrentDESCRIPTION"R fiber over 850 nm optics"REFERENCE"[IEEE 802.3 Std.], Section 52"::={ dot3MauType 36}dot3MauType10GigBaseW OBJECT-IDENTITYSTATUScurrentDESCRIPTION"W PCS/PMA, unknown PMD."REFERENCE"[IEEE 802.3 Std.], Section 49 and 50"::={ dot3MauType 37}dot3MauType10GigBaseEW OBJECT-IDENTITYSTATUScurrentDESCRIPTION"W fiber over 1550 nm optics"REFERENCE"[IEEE 802.3 Std.], Section 52"::={ dot3MauType 38}dot3MauType10GigBaseLW OBJECT-IDENTITYSTATUScurrentDESCRIPTION"W fiber over 1310 nm optics"REFERENCE"[IEEE 802.3 Std.], Section 52"::={ dot3MauType 39}dot3MauType10GigBaseSW OBJECT-IDENTITY
STATUScurrentDESCRIPTION"W fiber over 850 nm optics"REFERENCE"[IEEE 802.3 Std.], Section 52"::={ dot3MauType 40}---- The Basic Repeater MAU Table--rpMauTable OBJECT-TYPESYNTAXSEQUENCEOF RpMauEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Table of descriptive and status information
about the MAU(s) attached to the ports of a
repeater."::={ dot3RpMauBasicGroup 1}rpMauEntry OBJECT-TYPESYNTAX RpMauEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in the table, containing information
about a single MAU."INDEX{ rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex
}::={ rpMauTable 1}
RpMauEntry ::=SEQUENCE{
rpMauGroupIndex Integer32,
rpMauPortIndex Integer32,
rpMauIndex Integer32,
rpMauType AutonomousType,
rpMauStatus INTEGER,
rpMauMediaAvailable INTEGER,
rpMauMediaAvailableStateExits Counter32,
rpMauJabberState INTEGER,
rpMauJabberingStateEnters Counter32,
rpMauFalseCarriers Counter32}rpMauGroupIndex OBJECT-TYPESYNTAXInteger32(1..2147483647)MAX-ACCESSread-only-- read-only since originally an-- SMIv1 indexSTATUScurrentDESCRIPTION"This variable uniquely identifies the group
containing the port to which the MAU described
by this entry is connected.
Note: In practice, a group will generally be
a field-replaceable unit (i.e., module, card,
or board) that can fit in the physical system
enclosure, and the group number will correspond
to a number marked on the physical enclosure.
The group denoted by a particular value of this
object is the same as the group denoted by the
same value of rptrGroupIndex."REFERENCE"Reference RFC 2108, rptrGroupIndex."::={ rpMauEntry 1}rpMauPortIndex OBJECT-TYPESYNTAXInteger32(1..2147483647)MAX-ACCESSread-only-- read-only since originally an-- SMIv1 indexSTATUScurrentDESCRIPTION"This variable uniquely identifies the repeater
port within group rpMauGroupIndex to which the
MAU described by this entry is connected."REFERENCE"Reference RFC 2108, rptrPortIndex."::={ rpMauEntry 2}rpMauIndex OBJECT-TYPESYNTAXInteger32(1..2147483647)MAX-ACCESSread-only-- read-only since originally an-- SMIv1 indexSTATUScurrentDESCRIPTION"This variable uniquely identifies the MAU
described by this entry from among other
MAUs connected to the same port
(rpMauPortIndex)."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."::={ rpMauEntry 3}rpMauType OBJECT-TYPESYNTAXAutonomousTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object identifies the MAU type. Values for
standard IEEE 802.3 MAU types are defined above.
If the MAU type is unknown, the object identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is a
syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER
must be able to generate and recognize this
value."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."::={ rpMauEntry 4}rpMauStatus OBJECT-TYPESYNTAXINTEGER{other(1),unknown(2),operational(3),standby(4),shutdown(5),
reset(6)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The current state of the MAU. This object MAY
be implemented as a read-only object by those
agents and MAUs that do not implement software
control of the MAU state. Some agents may not
support setting the value of this object to some
of the enumerated values.
The value other(1) is returned if the MAU is in
a state other than one of the states 2 through
6.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
A MAU in the operational(3) state is fully
functional, operates, and passes signals to its
attached DTE or repeater port in accordance to
its specification.
A MAU in standby(4) state forces DI and CI to
idle and the media transmitter to idle or fault,
if supported. Standby(4) mode only applies to
link type MAUs. The state of
rpMauMediaAvailable is unaffected.
A MAU in shutdown(5) state assumes the same
condition on DI, CI, and the media transmitter
as though it were powered down or not connected.
The MAU MAY return other(1) value for the
rpMauJabberState and rpMauMediaAvailable objects
when it is in this state. For an AUI, this
state will remove power from the AUI.
Setting this variable to the value reset(6)
resets the MAU in the same manner as a
power-off, power-on cycle of at least one-half
second would. The agent is not required to
return the value reset (6).
Setting this variable to the value
operational(3), standby(4), or shutdown(5)
causes the MAU to assume the respective state
except that setting a mixing-type MAU or an AUI
to standby(4) will cause the MAU to enter the
shutdown state."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU."::={ rpMauEntry 5}rpMauMediaAvailable OBJECT-TYPESYNTAXINTEGER{other(1),unknown(2),available(3),notAvailable(4),remoteFault(5),invalidSignal(6),remoteJabber(7),remoteLinkLoss(8),
remoteTest(9),offline(10),autoNegError(11)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to
the link test fail state/low light function.
For an AUI or a coax (including broadband) MAU
this indicates whether or not loopback is
detected on the DI circuit. The value of this
attribute persists between packets for MAU types
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the
mediaAvailable state is not one of 2 through 11.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized. At power-up or following a
reset, the value of this attribute will be
unknown for AUI, coax, and 10BASE-FP MAUs. For
these MAUs loopback will be tested on each
transmission during which no collision is
detected. If DI is receiving input when DO
returns to IDL after a transmission and there
has been no collision during the transmission
then loopback will be detected. The value of
this attribute will only change during
non-collided transmissions for AUI, coax, and
10BASE-FP MAUs.
For 100Mbps and 1000Mbps MAUs, the enumerations
match the states within the respective link
integrity state diagrams, fig 32-16, 23-12 and
24-15 of sections 32, 23 and 24 of [IEEE802.3].
Any MAU which implements management of
auto-negotiation will map remote fault
indication to remote fault.
The value available(3) indicates that the link,
light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light,
or no loopback.
The value remoteFault(5) indicates that a fault
has been detected at the remote end of the link.
This value applies to 10BASE-FB, 100BASE-T4 Far
End Fault Indication and non-specified remote
faults from a system running auto-negotiation.
The values remoteJabber(7), remoteLinkLoss(8),
and remoteTest(9) SHOULD be used instead of
remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an
invalid signal has been received from the other
end of the link. invalidSignal(6) applies only
to MAUs of type 10BASE-FB.
Where an IEEE Std 802.3-2002 clause 22 MII
is present, a logic one in the remote fault bit
(reference section 22.2.4.2.8 of that document)
maps to the value remoteFault(5), and a logic
zero in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37
Auto-Negotiation will map the received Remote
Fault (RF1 and RF2) bit values for Offline to
offline(10), Link Failure to remoteFault(5) and
Auto-Negotiation Error to autoNegError(11)."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable."::={ rpMauEntry 6}rpMauMediaAvailableStateExits OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A count of the number of times that
rpMauMediaAvailable for this MAU instance leaves
the state available(3).
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of rptrMonitorPortLastChange."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter.
RFC 2108, rptrMonitorPortLastChange"::={ rpMauEntry 7}rpMauJabberState OBJECT-TYPESYNTAXINTEGER{other(1),unknown(2),noJabber(3),
jabbering(4)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
If the MAU is not jabbering the agent returns
noJabber(3). This is the 'normal' state.
If the MAU is in jabber state the agent returns
the jabbering(4) value."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberFlag."::={ rpMauEntry 8}rpMauJabberingStateEnters OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A count of the number of times that
mauJabberState for this MAU instance enters the
state jabbering(4). For MAUs of type
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, dot3MauType100BaseFX and
all 1000Mbps types, this counter will always
indicate zero.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of rptrMonitorPortLastChange."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter.
RFC 2108, rptrMonitorPortLastChange"::={ rpMauEntry 9}rpMauFalseCarriers OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A count of the number of false carrier events
during IDLE in 100BASE-X links. This counter
does not increment at the symbol rate. It can
increment after a valid carrier completion at a
maximum rate of once per 100 ms until the next
carrier event.
This counter increments only for MAUs of type
dot3MauType100BaseT4, dot3MauType100BaseTX, and
dot3MauType100BaseFX and all 1000Mbps types.
For all other MAU types, this counter will
always indicate zero.
The approximate minimum time for rollover of
this counter is 7.4 hours.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of rptrMonitorPortLastChange."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers.
RFC 2108, rptrMonitorPortLastChange"::={ rpMauEntry 10}
-- The rpJackTable applies to MAUs attached to repeaters-- which have one or more external jacks (connectors).rpJackTable OBJECT-TYPESYNTAXSEQUENCEOF RpJackEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Information about the external jacks attached
to MAUs attached to the ports of a repeater."::={ dot3RpMauBasicGroup 2}rpJackEntry OBJECT-TYPESYNTAX RpJackEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in the table, containing information
about a particular jack."INDEX{ rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex,
rpJackIndex
}::={ rpJackTable 1}
RpJackEntry ::=SEQUENCE{
rpJackIndex Integer32,
rpJackType JackType}rpJackIndex OBJECT-TYPESYNTAXInteger32(1..2147483647)
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This variable uniquely identifies the jack
described by this entry from among other jacks
attached to the same MAU (rpMauIndex)."::={ rpJackEntry 1}rpJackType OBJECT-TYPESYNTAXJackTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The jack connector type, as it appears on the
outside of the system."::={ rpJackEntry 2}---- The Basic Interface MAU Table--ifMauTable OBJECT-TYPESYNTAXSEQUENCEOF IfMauEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Table of descriptive and status information
about MAU(s) attached to an interface."::={ dot3IfMauBasicGroup 1}ifMauEntry OBJECT-TYPESYNTAX IfMauEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in the table, containing information
about a single MAU."INDEX{ ifMauIfIndex,
ifMauIndex
}::={ ifMauTable 1}
IfMauEntry ::=SEQUENCE{
ifMauIfIndex InterfaceIndex,
ifMauIndex Integer32,
ifMauType AutonomousType,
ifMauStatus INTEGER,
ifMauMediaAvailable INTEGER,
ifMauMediaAvailableStateExits Counter32,
ifMauJabberState INTEGER,
ifMauJabberingStateEnters Counter32,
ifMauFalseCarriers Counter32,
ifMauTypeList Integer32,
ifMauDefaultType AutonomousType,
ifMauAutoNegSupported TruthValue,
ifMauTypeListBits BITS,
ifMauHCFalseCarriers Counter64
}ifMauIfIndex OBJECT-TYPESYNTAXInterfaceIndexMAX-ACCESSread-only-- read-only since originally an-- SMIv1 indexSTATUScurrentDESCRIPTION"This variable uniquely identifies the interface
to which the MAU described by this entry is
connected."REFERENCE"RFC 2863, ifIndex"::={ ifMauEntry 1}ifMauIndex OBJECT-TYPESYNTAXInteger32(1..2147483647)MAX-ACCESSread-only-- read-only since originally an-- SMIv1 indexSTATUScurrentDESCRIPTION"This variable uniquely identifies the MAU
described by this entry from among other MAUs
connected to the same interface (ifMauIfIndex)."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."::={ ifMauEntry 2}ifMauType OBJECT-TYPESYNTAXAutonomousTypeMAX-ACCESSread-only
STATUScurrentDESCRIPTION"This object identifies the MAU type. Values for
standard IEEE 802.3 MAU types are defined above.
If the MAU type is unknown, the object identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is a
syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER
must be able to generate and recognize this
value.
This object represents the operational type of
the MAU, as determined by either (1) the result
of the auto-negotiation function or (2) if
auto-negotiation is not enabled or is not
implemented for this MAU, by the value of the
object ifMauDefaultType. In case (2), a set to
the object ifMauDefaultType will force the MAU
into the new operating mode."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."::={ ifMauEntry 3}ifMauStatus OBJECT-TYPESYNTAXINTEGER{other(1),unknown(2),operational(3),standby(4),shutdown(5),
reset(6)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The current state of the MAU. This object MAY
be implemented as a read-only object by those
agents and MAUs that do not implement software
control of the MAU state. Some agents may not
support setting the value of this object to some
of the enumerated values.
The value other(1) is returned if the MAU is in
a state other than one of the states 2 through
6.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
A MAU in the operational(3) state is fully
functional, operates, and passes signals to its
attached DTE or repeater port in accordance to
its specification.
A MAU in standby(4) state forces DI and CI to
idle and the media transmitter to idle or fault,
if supported. Standby(4) mode only applies to
link type MAUs. The state of
ifMauMediaAvailable is unaffected.
A MAU in shutdown(5) state assumes the same
condition on DI, CI, and the media transmitter
as though it were powered down or not connected.
The MAU MAY return other(1) value for the
ifMauJabberState and ifMauMediaAvailable objects
when it is in this state. For an AUI, this
state will remove power from the AUI.
Setting this variable to the value reset(6)
resets the MAU in the same manner as a
power-off, power-on cycle of at least one-half
second would. The agent is not required to
return the value reset (6).
Setting this variable to the value
operational(3), standby(4), or shutdown(5)
causes the MAU to assume the respective state
except that setting a mixing-type MAU or an AUI
to standby(4) will cause the MAU to enter the
shutdown state."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU."::={ ifMauEntry 4}ifMauMediaAvailable OBJECT-TYPESYNTAXINTEGER{other(1),unknown(2),available(3),notAvailable(4),remoteFault(5),invalidSignal(6),remoteJabber(7),remoteLinkLoss(8),
remoteTest(9),offline(10),autoNegError(11),pmdLinkFault(12),wisFrameLoss(13),wisSignalLoss(14),pcsLinkFault(15),excessiveBER(16),dxsLinkFault(17),pxsLinkFault(18)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to
the link test fail state/low light function.
For an AUI or a coax (including broadband) MAU
this indicates whether or not loopback is
detected on the DI circuit. The value of this
attribute persists between packets for MAU types
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the
mediaAvailable state is not one of 2 through 18.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized. At power-up or following a
reset, the value of this attribute will be
unknown for AUI, coax, and 10BASE-FP MAUs. For
these MAUs loopback will be tested on each
transmission during which no collision is
detected. If DI is receiving input when DO
returns to IDL after a transmission and there
has been no collision during the transmission
then loopback will be detected. The value of
this attribute will only change during
non-collided transmissions for AUI, coax, and
10BASE-FP MAUs.
For 100Mbps and 1000Mbps MAUs, the enumerations
match the states within the respective link
integrity state diagrams, fig 32-16, 23-12 and
24-15 of sections 32, 23 and 24 of [IEEE802.3].
Any MAU which implements management of
auto-negotiation will map remote fault
indication to remote fault.
The value available(3) indicates that the link,
light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light,
or no loopback.
The value remoteFault(5) indicates that a fault
has been detected at the remote end of the link.
This value applies to 10BASE-FB, 100BASE-T4 Far
End Fault Indication and non-specified remote
faults from a system running auto-negotiation.
The values remoteJabber(7), remoteLinkLoss(8),
and remoteTest(9) SHOULD be used instead of
remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an
invalid signal has been received from the other
end of the link. invalidSignal(6) applies only
to MAUs of type 10BASE-FB.
Where an IEEE Std 802.3-2002 clause 22 MII
is present, a logic one in the remote fault bit
(reference section 22.2.4.2.8 of that document)
maps to the value remoteFault(5), and a logic
zero in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37
Auto-Negotiation will map the received RF1 and
RF2 bit values for Offline to offline(10), Link
Failure to remoteFault(5) and Auto-Negotiation
Error to autoNegError(11).
For 10 Gb/s, the enumerations map to the states
within the Reconciliation Sublayer state diagram
as follows:
NoFault maps to the enumeration 'available(3)'
LocalFault maps to the enumeration
'notAvailable(4)'
RemoteFault maps to the enumeration
'remoteFault(5)'
The enumerations 'pmdLinkFault(12)',
'wisFrameLoss(13)', 'wisSignalLoss(14)',
'pcsLinkFault(15)', 'excessiveBER(16)', and
'dxsLinkFault(17)' and 'pxsLinkFault(18)' should
be used instead of the enumeration
'notAvailable(4)' where the reason for the local
fault can be identified through the use of the
MDIO Interface. Where multiple reasons for the
local fault state can be identified only the
highest precedence error should be reported.
The precedence in descending order is as
follows:
pxsLinkFault
pmdLinkFault
wisFrameLoss
wisSignalLoss
pcsLinkFault
excessiveBER
dxsLinkFault"REFERENCE"[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable."::={ ifMauEntry 5}ifMauMediaAvailableStateExits OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A count of the number of times that
ifMauMediaAvailable for this MAU instance leaves
the state available(3).
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter.
RFC 2863, ifCounterDiscontinuityTime."::={ ifMauEntry 6}ifMauJabberState OBJECT-TYPESYNTAXINTEGER{other(1),unknown(2),
noJabber(3),jabbering(4)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
If the MAU is not jabbering the agent returns
noJabber(3). This is the 'normal' state.
If the MAU is in jabber state the agent returns
the jabbering(4) value."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberFlag."::={ ifMauEntry 7}ifMauJabberingStateEnters OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A count of the number of times that
mauJabberState for this MAU instance enters the
state jabbering(4). This counter will always
indicate zero for MAUs of type dot3MauTypeAUI
and those of speeds above 10Mbps.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter.
RFC 2863, ifCounterDiscontinuityTime."::={ ifMauEntry 8}ifMauFalseCarriers OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A count of the number of false carrier events
during IDLE in 100BASE-X and 1000BASE-X links.
For all other MAU types, this counter will
always indicate zero. This counter does not
increment at the symbol rate.
It can increment after a valid carrier
completion at a maximum rate of once per 100 ms
for 100BASE-X and once per 10us for 1000BASE-X
until the next CarrierEvent.
This counter can roll over very quickly. A
management station is advised to poll the
ifMauHCFalseCarriers instead of this counter in
order to avoid loss of information.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers.
RFC 2863, ifCounterDiscontinuityTime."
::={ ifMauEntry 9}ifMauTypeList OBJECT-TYPESYNTAXInteger32MAX-ACCESSread-onlySTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This object has been deprecated in favour of
ifMauTypeListBits.
A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be.
The value is a sum which initially takes the
value zero. Then, for each type capability of
this MAU, 2 raised to the power noted below is
added to the sum. For example, a MAU which has
the capability to be only 10BASE-T would have a
value of 512 (2**9). In contrast, a MAU which
supports both 10Base-T (full duplex) and
100BASE-TX (full duplex) would have a value of
((2**11) + (2**16)) or 67584.
The powers of 2 assigned to the capabilities are
these:
Power Capability
0 other or unknown
1 AUI
2 10BASE-5
3 FOIRL
4 10BASE-2
5 10BASE-T duplex mode unknown
6 10BASE-FP
7 10BASE-FB
8 10BASE-FL duplex mode unknown
9 10BROAD36
10 10BASE-T half duplex mode
11 10BASE-T full duplex mode
12 10BASE-FL half duplex mode
13 10BASE-FL full duplex mode
14 100BASE-T4
15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode
17 100BASE-FX half duplex mode
18 100BASE-FX full duplex mode
19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode
If auto-negotiation is present on this MAU, this
object will map to ifMauAutoNegCapability."::={ ifMauEntry 10}ifMauDefaultType OBJECT-TYPESYNTAXAutonomousTypeMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object identifies the default
administrative baseband MAU type, to be used in
conjunction with the operational MAU type
denoted by ifMauType.
The set of possible values for this object is
the same as the set defined for the ifMauType
object.
This object represents the
administratively-configured type of the MAU. If
auto-negotiation is not enabled or is not
implemented for this MAU, the value of this
object determines the operational type of the
MAU. In this case, a set to this object will
force the MAU into the specified operating mode.
If auto-negotiation is implemented and enabled
for this MAU, the operational type of the MAU
is determined by auto-negotiation, and the value
of this object denotes the type to which the MAU
will automatically revert if/when
auto-negotiation is later disabled.
NOTE TO IMPLEMENTORS: It may be necessary to
provide for underlying hardware implementations
which do not follow the exact behavior specified
above. In particular, when
ifMauAutoNegAdminStatus transitions from enabled
to disabled, the agent implementation MUST
ensure that the operational type of the MAU (as
reported by ifMauType) correctly transitions to
the value specified by this object, rather than
continuing to operate at the value earlier
determined by the auto-negotiation function."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and
22.2.4.1.4."::={ ifMauEntry 11}ifMauAutoNegSupported OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates whether or not
auto-negotiation is supported on this MAU."::={ ifMauEntry 12}ifMauTypeListBits OBJECT-TYPESYNTAXBITS{bOther(0),-- other or unknownbAUI(1),-- AUI
b10base5(2),-- 10BASE-5bFoirl(3),-- FOIRLb10base2(4),-- 10BASE-2b10baseT(5),-- 10BASE-T duplex mode unknownb10baseFP(6),-- 10BASE-FPb10baseFB(7),-- 10BASE-FBb10baseFL(8),-- 10BASE-FL duplex mode unknownb10broad36(9),-- 10BROAD36b10baseTHD(10),-- 10BASE-T half duplex modeb10baseTFD(11),-- 10BASE-T full duplex modeb10baseFLHD(12),-- 10BASE-FL half duplex modeb10baseFLFD(13),-- 10BASE-FL full duplex modeb100baseT4(14),-- 100BASE-T4b100baseTXHD(15),-- 100BASE-TX half duplex mode
b100baseTXFD(16),-- 100BASE-TX full duplex modeb100baseFXHD(17),-- 100BASE-FX half duplex modeb100baseFXFD(18),-- 100BASE-FX full duplex modeb100baseT2HD(19),-- 100BASE-T2 half duplex modeb100baseT2FD(20),-- 100BASE-T2 full duplex modeb1000baseXHD(21),-- 1000BASE-X half duplex modeb1000baseXFD(22),-- 1000BASE-X full duplex modeb1000baseLXHD(23),-- 1000BASE-LX half duplex modeb1000baseLXFD(24),-- 1000BASE-LX full duplex modeb1000baseSXHD(25),-- 1000BASE-SX half duplex modeb1000baseSXFD(26),-- 1000BASE-SX full duplex modeb1000baseCXHD(27),-- 1000BASE-CX half duplex mode
b1000baseCXFD(28),-- 1000BASE-CX full duplex modeb1000baseTHD(29),-- 1000BASE-T half duplex modeb1000baseTFD(30),-- 1000BASE-T full duplex modeb10GbaseX(31),-- 10GBASE-Xb10GbaseLX4(32),-- 10GBASE-LX4b10GbaseR(33),-- 10GBASE-Rb10GbaseER(34),-- 10GBASE-ERb10GbaseLR(35),-- 10GBASE-LRb10GbaseSR(36),-- 10GBASE-SRb10GbaseW(37),-- 10GBASE-Wb10GbaseEW(38),-- 10GBASE-EWb10GbaseLW(39),-- 10GBASE-LWb10GbaseSW(40)-- 10GBASE-SW}MAX-ACCESSread-only
STATUScurrentDESCRIPTION"A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be.
If auto-negotiation is present on this MAU, this
object will map to ifMauAutoNegCapabilityBits.
Note that this MAU may be capable of operating
as a MAU type that is beyond the scope of this
MIB. This is indicated by returning the
bit value bOther in addition to any bit values
for capabilities that are listed above."::={ ifMauEntry 13}ifMauHCFalseCarriers OBJECT-TYPESYNTAXCounter64MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A count of the number of false carrier events
during IDLE in 100BASE-X and 1000BASE-X links.
For all other MAU types, this counter will
always indicate zero. This counter does not
increment at the symbol rate.
This counter is a 64 bit version of
ifMauFalseCarriers. Since the 32 bit version of
this counter can roll over very quickly,
management stations are advised to poll the
64 bit version instead in order to avoid loss
of information.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers.
RFC 2863, ifCounterDiscontinuityTime."::={ ifMauEntry 14}-- The ifJackTable applies to MAUs attached to interfaces-- which have one or more external jacks (connectors).ifJackTable OBJECT-TYPESYNTAXSEQUENCEOF IfJackEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Information about the external jacks attached
to MAUs attached to an interface."::={ dot3IfMauBasicGroup 2}ifJackEntry OBJECT-TYPESYNTAX IfJackEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in the table, containing information
about a particular jack."INDEX{ ifMauIfIndex,
ifMauIndex,
ifJackIndex
}::={ ifJackTable 1}
IfJackEntry ::=SEQUENCE{
ifJackIndex Integer32,
ifJackType JackType
}ifJackIndex OBJECT-TYPESYNTAXInteger32(1..2147483647)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This variable uniquely identifies the jack
described by this entry from among other jacks
attached to the same MAU."::={ ifJackEntry 1}ifJackType OBJECT-TYPESYNTAXJackTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The jack connector type, as it appears on the
outside of the system."::={ ifJackEntry 2}---- The MAU Auto-Negotiation Table--ifMauAutoNegTable OBJECT-TYPESYNTAXSEQUENCEOF IfMauAutoNegEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Configuration and status objects for the
auto-negotiation function of MAUs attached to
interfaces.
The ifMauAutoNegTable applies to systems in
which auto-negotiation is supported on one or
more MAUs attached to interfaces. Note that if
auto-negotiation is present and enabled, the
ifMauType object reflects the result of the
auto-negotiation function."::={ dot3IfMauAutoNegGroup 1}ifMauAutoNegEntry OBJECT-TYPESYNTAX IfMauAutoNegEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in the table, containing configuration
and status information for the auto-negotiation
function of a particular MAU."INDEX{ ifMauIfIndex,
ifMauIndex
}::={ ifMauAutoNegTable 1}
IfMauAutoNegEntry ::=SEQUENCE{
ifMauAutoNegAdminStatus INTEGER,
ifMauAutoNegRemoteSignaling INTEGER,
ifMauAutoNegConfig INTEGER,
ifMauAutoNegCapability Integer32,
ifMauAutoNegCapAdvertised Integer32,
ifMauAutoNegCapReceived Integer32,
ifMauAutoNegRestart INTEGER,
ifMauAutoNegCapabilityBits BITS,
ifMauAutoNegCapAdvertisedBits BITS,
ifMauAutoNegCapReceivedBits BITS,
ifMauAutoNegRemoteFaultAdvertised INTEGER,
ifMauAutoNegRemoteFaultReceived INTEGER}ifMauAutoNegAdminStatus OBJECT-TYPESYNTAXINTEGER{enabled(1),disabled(2)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"Setting this object to enabled(1) will cause
the interface which has the auto-negotiation
signaling ability to be enabled.
If the value of this object is disabled(2) then
the interface will act as it would if it had no
auto-negotiation signaling. Under these
conditions, an IEEE 802.3 MAU will immediately
be forced to the state indicated by the value of
the object ifMauDefaultType.
NOTE TO IMPLEMENTORS: When
ifMauAutoNegAdminStatus transitions from enabled
to disabled, the agent implementation MUST
ensure that the operational type of the MAU (as
reported by ifMauType) correctly transitions to
the value specified by the ifMauDefaultType
object, rather than continuing to operate at the
value earlier determined by the auto-negotiation
function."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.2,
aAutoNegAdminState and 30.6.1.2.2,
acAutoNegAdminControl."::={ ifMauAutoNegEntry 1}ifMauAutoNegRemoteSignaling OBJECT-TYPESYNTAXINTEGER{detected(1),notdetected(2)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A value indicating whether the remote end of
the link is using auto-negotiation signaling. It
takes the value detected(1) if and only if,
during the previous link negotiation, FLP Bursts
were received."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.3,
aAutoNegRemoteSignaling."::={ ifMauAutoNegEntry 2}ifMauAutoNegConfig OBJECT-TYPESYNTAXINTEGER{other(1),configuring(2),
complete(3),disabled(4),parallelDetectFail(5)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A value indicating the current status of the
auto-negotiation process. The enumeration
parallelDetectFail(5) maps to a failure in
parallel detection as defined in 28.2.3.1 of
[IEEE 802.3 Std]."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.4,
aAutoNegAutoConfig."::={ ifMauAutoNegEntry 4}ifMauAutoNegCapability OBJECT-TYPESYNTAXInteger32MAX-ACCESSread-onlySTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This object has been deprecated in favour of
ifMauAutoNegCapabilityBits.
A value that uniquely identifies the set of
capabilities of the local auto-negotiation
entity. The value is a sum which initially
takes the value zero. Then, for each capability
of this interface, 2 raised to the power noted
below is added to the sum. For example, an
interface which has the capability to support
only 100Base-TX half duplex would have a value
of 32768 (2**15). In contrast, an interface
which supports both 100Base-TX half duplex and
and 100Base-TX full duplex would have a value of
98304 ((2**15) + (2**16)).
The powers of 2 assigned to the capabilities are
these:
Power Capability
0 other or unknown
(1-9) (reserved)
10 10BASE-T half duplex mode
11 10BASE-T full duplex mode
12 (reserved)
13 (reserved)
14 100BASE-T4
15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode
17 (reserved)
18 (reserved)
19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode
Note that interfaces that support this MIB may
have capabilities that extend beyond the scope
of this MIB."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."::={ ifMauAutoNegEntry 5}ifMauAutoNegCapAdvertised OBJECT-TYPESYNTAXInteger32MAX-ACCESSread-writeSTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This object has been deprecated in favour of
ifMauAutoNegCapAdvertisedBits.
A value that uniquely identifies the set of
capabilities advertised by the local
auto-negotiation entity. Refer to
ifMauAutoNegCapability for a description of the
possible values of this object.
Capabilities in this object that are not
available in ifMauAutoNegCapability cannot be
enabled."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."::={ ifMauAutoNegEntry 6}ifMauAutoNegCapReceived OBJECT-TYPESYNTAXInteger32MAX-ACCESSread-onlySTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This object has been deprecated in favour of
ifMauAutoNegCapReceivedBits.
A value that uniquely identifies the set of
capabilities received from the remote
auto-negotiation entity. Refer to
ifMauAutoNegCapability for a description of the
possible values of this object.
Note that interfaces that support this MIB may
be attached to remote auto-negotiation entities
which have capabilities beyond the scope of this
MIB."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."::={ ifMauAutoNegEntry 7}
ifMauAutoNegRestart OBJECT-TYPESYNTAXINTEGER{restart(1),norestart(2)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"If the value of this object is set to
restart(1) then this will force auto-negotiation
to begin link renegotiation. If auto-negotiation
signaling is disabled, a write to this object
has no effect.
Setting the value of this object to norestart(2)
has no effect."REFERENCE"[IEEE 802.3 Std], 30.6.1.2.1,
acAutoNegRestartAutoConfig."::={ ifMauAutoNegEntry 8}ifMauAutoNegCapabilityBits OBJECT-TYPESYNTAXBITS{bOther(0),-- other or unknownb10baseT(1),-- 10BASE-T half duplex modeb10baseTFD(2),-- 10BASE-T full duplex modeb100baseT4(3),-- 100BASE-T4
b100baseTX(4),-- 100BASE-TX half duplex modeb100baseTXFD(5),-- 100BASE-TX full duplex modeb100baseT2(6),-- 100BASE-T2 half duplex modeb100baseT2FD(7),-- 100BASE-T2 full duplex modebfdxPause(8),-- PAUSE for full-duplex linksbfdxAPause(9),-- Asymmetric PAUSE for full-duplex-- linksbfdxSPause(10),-- Symmetric PAUSE for full-duplex-- linksbfdxBPause(11),-- Asymmetric and Symmetric PAUSE for-- full-duplex linksb1000baseX(12),-- 1000BASE-X, -LX, -SX, -CX half-- duplex modeb1000baseXFD(13),-- 1000BASE-X, -LX, -SX, -CX full-- duplex mode
b1000baseT(14),-- 1000BASE-T half duplex modeb1000baseTFD(15)-- 1000BASE-T full duplex mode}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A value that uniquely identifies the set of
capabilities of the local auto-negotiation
entity. Note that interfaces that support this
MIB may have capabilities that extend beyond the
scope of this MIB.
Note that the local auto-negotiation entity may
support some capabilities beyond the scope of
this MIB. This is indicated by returning the
bit value bOther in addition to any bit values
for capabilities that are listed above."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."::={ ifMauAutoNegEntry 9}ifMauAutoNegCapAdvertisedBits OBJECT-TYPESYNTAXBITS{bOther(0),-- other or unknownb10baseT(1),-- 10BASE-T half duplex modeb10baseTFD(2),-- 10BASE-T full duplex mode
b100baseT4(3),-- 100BASE-T4b100baseTX(4),-- 100BASE-TX half duplex modeb100baseTXFD(5),-- 100BASE-TX full duplex modeb100baseT2(6),-- 100BASE-T2 half duplex modeb100baseT2FD(7),-- 100BASE-T2 full duplex modebFdxPause(8),-- PAUSE for full-duplex linksbFdxAPause(9),-- Asymmetric PAUSE for full-duplex-- linksbFdxSPause(10),-- Symmetric PAUSE for full-duplex-- linksbFdxBPause(11),-- Asymmetric and Symmetric PAUSE for-- full-duplex linksb1000baseX(12),-- 1000BASE-X, -LX, -SX, -CX half-- duplex modeb1000baseXFD(13),-- 1000BASE-X, -LX, -SX, -CX full
-- duplex modeb1000baseT(14),-- 1000BASE-T half duplex modeb1000baseTFD(15)-- 1000BASE-T full duplex mode}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"A value that uniquely identifies the set of
capabilities advertised by the local
auto-negotiation entity.
Capabilities in this object that are not
available in ifMauAutoNegCapabilityBits cannot
be enabled.
Note that the local auto-negotiation entity may
advertise some capabilities beyond the scope of
this MIB. This is indicated by returning the
bit value bOther in addition to any bit values
for capabilities that are listed above."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."::={ ifMauAutoNegEntry 10}ifMauAutoNegCapReceivedBits OBJECT-TYPESYNTAXBITS{bOther(0),-- other or unknownb10baseT(1),-- 10BASE-T half duplex modeb10baseTFD(2),-- 10BASE-T full duplex mode
b100baseT4(3),-- 100BASE-T4b100baseTX(4),-- 100BASE-TX half duplex modeb100baseTXFD(5),-- 100BASE-TX full duplex modeb100baseT2(6),-- 100BASE-T2 half duplex modeb100baseT2FD(7),-- 100BASE-T2 full duplex modebFdxPause(8),-- PAUSE for full-duplex linksbFdxAPause(9),-- Asymmetric PAUSE for full-duplex-- linksbFdxSPause(10),-- Symmetric PAUSE for full-duplex-- linksbFdxBPause(11),-- Asymmetric and Symmetric PAUSE for-- full-duplex linksb1000baseX(12),-- 1000BASE-X, -LX, -SX, -CX half-- duplex modeb1000baseXFD(13),-- 1000BASE-X, -LX, -SX, -CX full
-- duplex modeb1000baseT(14),-- 1000BASE-T half duplex modeb1000baseTFD(15)-- 1000BASE-T full duplex mode}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A value that uniquely identifies the set of
capabilities received from the remote
auto-negotiation entity.
Note that interfaces that support this MIB may
be attached to remote auto-negotiation entities
which have capabilities beyond the scope of this
MIB. This is indicated by returning the bit
value bOther in addition to any bit values for
capabilities that are listed above."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."::={ ifMauAutoNegEntry 11}ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPESYNTAXINTEGER{noError(1),offline(2),linkFailure(3),
autoNegError(4)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"A value that identifies any local fault
indications that this MAU has detected and will
advertise at the next auto-negotiation
interaction for 1000Mbps MAUs."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."::={ ifMauAutoNegEntry 12}ifMauAutoNegRemoteFaultReceived OBJECT-TYPESYNTAXINTEGER{noError(1),offline(2),linkFailure(3),autoNegError(4)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A value that identifies any fault indications
received from the far end of a link by the
local auto-negotiation entity for 1000Mbps
MAUs."REFERENCE"[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."::={ ifMauAutoNegEntry 13}---- The Basic Broadband MAU Table--broadMauBasicTable OBJECT-TYPESYNTAXSEQUENCEOF BroadMauBasicEntry
MAX-ACCESSnot-accessibleSTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This entire table has been deprecated. There
have been no reported implementations of this
table, and it is unlikely that there ever will
be. IEEE recommends that broadband MAU types
should not be used for new installations.
Table of descriptive and status information
about the broadband MAUs connected to
interfaces."::={ dot3BroadMauBasicGroup 1}broadMauBasicEntry OBJECT-TYPESYNTAX BroadMauBasicEntry
MAX-ACCESSnot-accessibleSTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
An entry in the table, containing information
about a single broadband MAU."INDEX{ broadMauIfIndex,
broadMauIndex
}::={ broadMauBasicTable 1}
BroadMauBasicEntry ::=SEQUENCE{
broadMauIfIndex InterfaceIndex,
broadMauIndex Integer32,
broadMauXmtRcvSplitType INTEGER,
broadMauXmtCarrierFreq Integer32,
broadMauTranslationFreq Integer32}broadMauIfIndex OBJECT-TYPESYNTAXInterfaceIndexMAX-ACCESSread-only-- read-only since originally an-- SMIv1 indexSTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This variable uniquely identifies the interface
to which the MAU described by this entry is
connected."REFERENCE"Reference RFC 2863, ifIndex."::={ broadMauBasicEntry 1}broadMauIndex OBJECT-TYPESYNTAXInteger32(1..2147483647)MAX-ACCESSread-only-- read-only since originally an
-- SMIv1 indexSTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This variable uniquely identifies the MAU
connected to interface broadMauIfIndex that is
described by this entry."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."::={ broadMauBasicEntry 2}broadMauXmtRcvSplitType OBJECT-TYPESYNTAXINTEGER{other(1),single(2),dual(3)}MAX-ACCESSread-onlySTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This object indicates the type of frequency
multiplexing/cabling system used to separate the
transmit and receive paths for the 10BROAD36
MAU.
The value other(1) is returned if the split type
is not either single or dual.
The value single(2) indicates a single cable
system. The value dual(3) indicates a dual
cable system, offset normally zero."
REFERENCE"[IEEE 802.3 Std], 30.5.1.1.8,
aBbMAUXmitRcvSplitType."::={ broadMauBasicEntry 3}broadMauXmtCarrierFreq OBJECT-TYPESYNTAXInteger32MAX-ACCESSread-onlySTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This variable indicates the transmit carrier
frequency of the 10BROAD36 MAU in MHz/4; that
is, in units of 250 kHz."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.9,
aBroadbandFrequencies.xmitCarrierFrequency."::={ broadMauBasicEntry 4}broadMauTranslationFreq OBJECT-TYPESYNTAXInteger32MAX-ACCESSread-onlySTATUSdeprecatedDESCRIPTION"********* THIS OBJECT IS DEPRECATED **********
This variable indicates the translation offset
frequency of the 10BROAD36 MAU in MHz/4; that
is, in units of 250 kHz."REFERENCE"[IEEE 802.3 Std], 30.5.1.1.9,
aBroadbandFrequencies.translationFrequency."::={ broadMauBasicEntry 5}-- Notifications for use by 802.3 MAUs
snmpDot3MauTraps OBJECTIDENTIFIER::={ snmpDot3MauMgt 0}rpMauJabberTrap NOTIFICATION-TYPEOBJECTS{ rpMauJabberState }STATUScurrentDESCRIPTION"This trap is sent whenever a managed repeater
MAU enters the jabber state.
The agent MUST throttle the generation of
consecutive rpMauJabberTraps so that there is at
least a five-second gap between them."REFERENCE"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
notification."::={ snmpDot3MauTraps 1}ifMauJabberTrap NOTIFICATION-TYPEOBJECTS{ ifMauJabberState }STATUScurrentDESCRIPTION"This trap is sent whenever a managed interface
MAU enters the jabber state.
The agent MUST throttle the generation of
consecutive ifMauJabberTraps so that there is at
least a five-second gap between them."REFERENCE"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
notification."::={ snmpDot3MauTraps 2}-- Conformance informationmauModConf
OBJECTIDENTIFIER::={ mauMod 1}
mauModCompls
OBJECTIDENTIFIER::={ mauModConf 1}mauModObjGrps
OBJECTIDENTIFIER::={ mauModConf 2}mauModNotGrps
OBJECTIDENTIFIER::={ mauModConf 3}-- Object groupsmauRpGrpBasic OBJECT-GROUPOBJECTS{ rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex,
rpMauType,
rpMauStatus,
rpMauMediaAvailable,
rpMauMediaAvailableStateExits,
rpMauJabberState,
rpMauJabberingStateEnters
}STATUScurrentDESCRIPTION"Basic conformance group for MAUs attached to
repeater ports. This group is also the
conformance specification for RFC 1515
implementations."::={ mauModObjGrps 1}mauRpGrp100Mbs OBJECT-GROUP
OBJECTS{ rpMauFalseCarriers }STATUScurrentDESCRIPTION"Conformance group for MAUs attached to
repeater ports with 100 Mb/s or greater
capability."::={ mauModObjGrps 2}mauRpGrpJack OBJECT-GROUPOBJECTS{ rpJackType }STATUScurrentDESCRIPTION"Conformance group for MAUs attached to
repeater ports with managed jacks."::={ mauModObjGrps 3}mauIfGrpBasic OBJECT-GROUPOBJECTS{ ifMauIfIndex,
ifMauIndex,
ifMauType,
ifMauStatus,
ifMauMediaAvailable,
ifMauMediaAvailableStateExits,
ifMauJabberState,
ifMauJabberingStateEnters
}STATUScurrentDESCRIPTION"Basic conformance group for MAUs attached to
interfaces. This group also provides a
conformance specification for RFC 1515
implementations."::={ mauModObjGrps 4}
mauIfGrp100Mbs OBJECT-GROUPOBJECTS{ ifMauFalseCarriers,
ifMauTypeList,
ifMauDefaultType,
ifMauAutoNegSupported
}STATUSdeprecatedDESCRIPTION"********* THIS GROUP IS DEPRECATED **********
Conformance group for MAUs attached to
interfaces with 100 Mb/s capability.
This object group has been deprecated in favor
of mauIfGrpHighCapacity."::={ mauModObjGrps 5}mauIfGrpJack OBJECT-GROUPOBJECTS{ ifJackType }STATUScurrentDESCRIPTION"Conformance group for MAUs attached to
interfaces with managed jacks."::={ mauModObjGrps 6}mauIfGrpAutoNeg OBJECT-GROUPOBJECTS{ ifMauAutoNegAdminStatus,
ifMauAutoNegRemoteSignaling,
ifMauAutoNegConfig,
ifMauAutoNegCapability,
ifMauAutoNegCapAdvertised,
ifMauAutoNegCapReceived,
ifMauAutoNegRestart
}STATUSdeprecatedDESCRIPTION"********* THIS GROUP IS DEPRECATED **********
Conformance group for MAUs attached to
interfaces with managed auto-negotiation.
This object group has been deprecated in favor
of mauIfGrpAutoNeg2."::={ mauModObjGrps 7}mauBroadBasic OBJECT-GROUPOBJECTS{ broadMauIfIndex,
broadMauIndex,
broadMauXmtRcvSplitType,
broadMauXmtCarrierFreq,
broadMauTranslationFreq
}STATUSdeprecatedDESCRIPTION"********* THIS GROUP IS DEPRECATED **********
Conformance group for broadband MAUs attached
to interfaces.
This object group is deprecated. There have
been no reported implementations of this group,
and it was felt to be unlikely that there will
be any future implementations."::={ mauModObjGrps 8}mauIfGrpHighCapacity OBJECT-GROUPOBJECTS{ ifMauFalseCarriers,
ifMauTypeListBits,
ifMauDefaultType,
ifMauAutoNegSupported
}
STATUScurrentDESCRIPTION"Conformance group for MAUs attached to
interfaces with 100 Mb/s or greater capability."::={ mauModObjGrps 9}mauIfGrpAutoNeg2 OBJECT-GROUPOBJECTS{ ifMauAutoNegAdminStatus,
ifMauAutoNegRemoteSignaling,
ifMauAutoNegConfig,
ifMauAutoNegCapabilityBits,
ifMauAutoNegCapAdvertisedBits,
ifMauAutoNegCapReceivedBits,
ifMauAutoNegRestart
}STATUScurrentDESCRIPTION"Conformance group for MAUs attached to
interfaces with managed auto-negotiation."::={ mauModObjGrps 10}mauIfGrpAutoNeg1000Mbps OBJECT-GROUPOBJECTS{ ifMauAutoNegRemoteFaultAdvertised,
ifMauAutoNegRemoteFaultReceived
}STATUScurrentDESCRIPTION"Conformance group for 1000Mbps MAUs attached to
interfaces with managed auto-negotiation."::={ mauModObjGrps 11}mauIfGrpHCStats OBJECT-GROUP
OBJECTS{ ifMauHCFalseCarriers }STATUScurrentDESCRIPTION"Conformance for high capacity statistics for
MAUs attached to interfaces"::={ mauModObjGrps 12}-- Notification groupsrpMauNotifications NOTIFICATION-GROUPNOTIFICATIONS{ rpMauJabberTrap }STATUScurrentDESCRIPTION"Notifications for repeater MAUs."::={ mauModNotGrps 1}ifMauNotifications NOTIFICATION-GROUPNOTIFICATIONS{ ifMauJabberTrap }STATUScurrentDESCRIPTION"Notifications for interface MAUs."::={ mauModNotGrps 2}-- CompliancesmauModRpCompl MODULE-COMPLIANCESTATUSdeprecatedDESCRIPTION"******** THIS COMPLIANCE IS DEPRECATED ********
Compliance for MAUs attached to repeater
ports.
This compliance is deprecated and replaced by
mauModRpCompl2, which corrects an oversight by
allowing rpMauStatus to be implemented
read-only."MODULE-- this moduleMANDATORY-GROUPS{ mauRpGrpBasic }GROUP mauRpGrp100Mbs
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have 100Mb/s or
greater capability."GROUP mauRpGrpJack
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."GROUP rpMauNotifications
DESCRIPTION"Implementation of this group is recommended
for MAUs attached to repeater ports."::={ mauModCompls 1}mauModIfCompl MODULE-COMPLIANCESTATUSdeprecatedDESCRIPTION"******** THIS COMPLIANCE IS DEPRECATED ********
Compliance for MAUs attached to interfaces.
This compliance is deprecated and replaced by
mauModIfCompl2."MODULE-- this moduleMANDATORY-GROUPS{ mauIfGrpBasic }GROUP mauIfGrp100Mbs
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have 100Mb/s
capability."GROUP mauIfGrpJack
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."GROUP mauIfGrpAutoNeg
DESCRIPTION"Implementation of this group is mandatory
for MAUs which support managed
auto-negotiation."GROUP mauBroadBasic
DESCRIPTION"Implementation of this group is mandatory
for broadband MAUs."GROUP ifMauNotifications
DESCRIPTION"Implementation of this group is recommended
for MAUs attached to interfaces."::={ mauModCompls 2}mauModIfCompl2 MODULE-COMPLIANCESTATUSdeprecatedDESCRIPTION"******** THIS COMPLIANCE IS DEPRECATED ********
Compliance for MAUs attached to interfaces.
This compliance is deprecated and replaced by
mauModIfCompl3."MODULE-- this moduleMANDATORY-GROUPS{ mauIfGrpBasic }GROUP mauIfGrpHighCapacity
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have 100Mb/s
or greater capability."GROUP mauIfGrpJack
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."GROUP mauIfGrpAutoNeg2
DESCRIPTION"Implementation of this group is mandatory
for MAUs which support managed
auto-negotiation."GROUP mauIfGrpAutoNeg1000Mbps
DESCRIPTION"Implementation of this group is mandatory
for MAUs which have 1000Mb/s or greater
capability and support managed
auto-negotiation."GROUP ifMauNotifications
DESCRIPTION"Implementation of this group is recommended
for MAUs attached to interfaces."OBJECT ifMauStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."::={ mauModCompls 3}mauModRpCompl2 MODULE-COMPLIANCESTATUScurrentDESCRIPTION"Compliance for MAUs attached to repeater
ports.
Note that compliance with this compliance
statement requires compliance with the
snmpRptrModCompl MODULE-COMPLIANCE statement of
the SNMP-REPEATER-MIB (RFC 2108)."MODULE-- this moduleMANDATORY-GROUPS{ mauRpGrpBasic }
GROUP mauRpGrp100Mbs
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have 100Mb/s or
greater capability."GROUP mauRpGrpJack
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."GROUP rpMauNotifications
DESCRIPTION"Implementation of this group is recommended
for MAUs attached to repeater ports."OBJECT rpMauStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."::={ mauModCompls 4}mauModIfCompl3 MODULE-COMPLIANCESTATUScurrentDESCRIPTION"Compliance for MAUs attached to interfaces.
Note that compliance with this compliance
statement requires compliance with the
ifCompliance3 MODULE-COMPLIANCE statement of the
IF-MIB (RFC 2863) and the dot3Compliance2
MODULE-COMPLIANCE statement of the
EtherLike-MIB (RFC3635)."MODULE-- this moduleMANDATORY-GROUPS{ mauIfGrpBasic }GROUP mauIfGrpHighCapacity
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have 100Mb/s
or greater capability."GROUP mauIfGrpHCStats
DESCRIPTION"Implementation of this group is mandatory
for MAUs which have 1000Mb/s capacity, and
is recommended for MAUs which have 100Mb/s
capacity."GROUP mauIfGrpJack
DESCRIPTION"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."GROUP mauIfGrpAutoNeg2
DESCRIPTION"Implementation of this group is mandatory
for MAUs which support managed
auto-negotiation."GROUP mauIfGrpAutoNeg1000Mbps
DESCRIPTION"Implementation of this group is mandatory
for MAUs which have 1000Mb/s or greater
capability and support managed
auto-negotiation."GROUP ifMauNotifications
DESCRIPTION"Implementation of this group is recommended
for MAUs attached to interfaces."OBJECT ifMauStatus
MIN-ACCESSread-onlyDESCRIPTION"Write access is not required."::={ mauModCompls 5}END